Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1036

reference
421-tree-1
name
1036
tree-preservation-order

undefined

421-tpo-1
uprn
address-text
point
POINT (-1.011202 50.890850)
geometry
MULTIPOLYGON (((-1.011131 50.890842,-1.011134 50.890856,-1.011144 50.890869,-1.011159 50.890879,-1.011179 50.890885,-1.011201 50.890888,-1.011223 50.890886,-1.011243 50.890879,-1.011259 50.890869,-1.011269 50.890857,-1.011273 50.890843,-1.011270 50.890829,-1.011260 50.890817,-1.011245 50.890807,-1.011225 50.890800,-1.011203 50.890798,-1.011181 50.890800,-1.011161 50.890806,-1.011145 50.890816,-1.011135 50.890828,-1.011131 50.890842)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL